Skip to main content

List Associated Teams

Description

Microsoft Teams: List Associated Teams plugin step lists your associated teams.

References

Permissions

Following are the required permissions:

Permission typePermission (from least to most privileged)
Delegated (work or school account)offline_access, Team.ReadBasic.All, TeamSettings.Read.All,TeamSettings.ReadWrite.All

Configurations

No.Field NameDescription
1Step NameName of the step. This name has to be unique in a single workflow.
Connection:
2Tenant IDSelect the Tenant ID.
For more details, see connection documentation.
The field data type is String. This is a mandatory field.
3Client IDSelect the Client ID.
For more details, see connection documentation.
The field data type is String.This is a mandatory field.
4Accept Value as variable/staticLeave checkbox unchecked to accept Client Secret from a field in the previous steps of the stream using a drop down list.
Else enable checkbox for Client Secret field to appear as Text box.
5Client SecretSpecify the Client Secret of Microsoft Teams application. Client Secret is entered using a widget.
If the Accept Values as variable/static check box is selected, then the Client Secret field appears as text box and accepts static values or variables. Else, select Client Secret from the drop down list.
The field data type is String. This is a mandatory field.
6Accept Value as variable/staticLeave checkbox unchecked to accept Refresh Token from a field in the previous steps of the stream using a drop down list.
Else enable checkbox for Refresh Token field to appear as Text box.
7Refresh TokenProvide the Refresh Token provided by authorization grant flow.
If the Accept Values as variable/static check box is selected, then the Refresh Token field appears as text box and accepts static values or variables. Else, select Refresh Token from the drop down list.
The field data type is String. This is a mandatory field.
8Test ConnectionVerifies whether the connection is established or not.
Note: For the purpose of verification fields coming from previous steps are not allowed since field values can only be accessed when workflow is in running state. Static values and environment variables are allowed.